-
Notifications
You must be signed in to change notification settings - Fork 124
Improve ExitStatus.description
for signals.
#1302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This PR uses the `sys_signame` array present on many UNIX-like systems to derive a better description for values of type `ExitStatus` and `ExitTest.Condition`. (On Linux, the equivalent `sigabbrev_np()` is used. Windows and WASI don't have an equivalent API.)
@swift-ci test |
@finagolfin and @3405691582 Could you smoke-test this on Android/OpenBSD please? Thanks! |
@swift-ci test |
@swift-ci test |
@swift-ci test |
(FWIW, the toolchain successfully built after merge on OpenBSD.) |
Building this Testing repo natively on Android after this pull worked fine, but I could not build the tests with the following error:
Does compiling Testing trunk currently require a recent trunk snapshot toolchain? I'm building it with an older June 17 trunk snapshot toolchain that I natively built on Android too, so I'll need to build one of the latest trunk snapshot toolchains first if so. Anyway, the exit tests are disabled on Android, so this test won't be run there anyway. |
@finagolfin That sounds like swiftlang/swift#84184. Looks like a bug in 6.2 with move-only types, but I don't have more info. |
This PR uses the
sys_signame
array present on many UNIX-like systems to derive a better description for values of typeExitStatus
andExitTest.Condition
. (On Linux, the equivalentsigabbrev_np()
is used. Windows and WASI don't have an equivalent API.)Before:
After:
Checklist: